Initial build of Exchange 2013 SP1

IPS: Comcast

To date:

Change outbound SMTP port from 110 to 587 for Comcast

Established Comcast as smart host

Setup internal receipients as user@mydomain.com in mail flow default policy. Since Comcast blocks inbound port 25, I have a mailhop and MX records set to forward on port 2525

Ports forwarded to exchange IP

IMAP 143

POP3 110

SMTP 25

Comcast 587

SSL 993

Mailhop 2525 to 25

I can successfully send a eMail to an external domain eMail address and it shows coming from user@mydomain.com. If I reply or send an eMail to user@mydomain.com, it does not come through. It comes back to sender as undeliverable. One bounce back had a full session trace.  I see it picked up by the mailhop at the MX of mydomain.com. From what I can see, it got sent to router. The message I see is Recipient address rejected: undeliverable address: User unkown. I cannot validate that it was presented on port 2525 and sent over to 25 then exchange. However, the rejection seems to indicate that Exchange rejected it.

What am I missing to connect to the recipient mailbox?

John

Hi,

Based on your description, my understanding is: You can send emails to remote domains successfully, but failed to receive emails. If there are any misunderstanding, please let me know.

Is there any NDR message we can refer to troubleshoot this issue?

Does this issue occur on all the inbound emails?

I suggest we firstly use the telnet command to see which command fails:

http://support.microsoft.com/kb/153119

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Hi,

Is there any update on this thread?

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Sorry for the delay. I have been out-of-town at a client. I will work on this week and report back.

I am attaching the link to the NDR transport chain. GoDaddy manages the MX records and points to the router IP address from Comcast. Since Comcast blocks inbound port 25, I have a mail hop intercept and forward on port 2525. In the router I have UPnP setup to move inbound port 2525 to port 25 which is forwarded to the IP address of the exchange server.

Outbound eMail goes through Comcast as a smart host. Reply gets rejected and an external eMail addressed to the myname@longsoho.com is rejected as well. in Exchange, recipients are addressed as @longsoho.com. Is there something else I have to do to get to the mailbox on internal domain longsoho.local?

https://onedrive.live.com/redir?resid=418500A441DD106A!7440&authkey=!AB9BGjn64gpI9j8&ithint=file%2cpdf

I successfully did the port 25 SMTP test. However, this is outbound. My problem is inbound to longsoho.com then connecting the longsoho.local mailbox.

Is your ad setup for longsoho.com? or only longsoho.local?

AD only shows longsoho.local. Is this the issue & how do I add longsoho.com to AD correctly?

No, not an issue just a inquiry.

If you log into the ECP admin portal, Recipients -> Edit User -> General -> More Options.. -> Organizational Unit: (is this pointing to the correct OU?)

Under 'email address' is the SMTP address labeled correctly with primary as User@longsoho.com?

It is pointing to longsoho.local/users for OU

eMail address is user@longsoho.com in SMTP

is that the correct OU were the user is stored?

I am using an alias in Exchange so:

AD user is longsfi001@longsoho.local

eMail alais is John.Lenz@longsoho.com

Address seen by external eMail recipient is John.Lenz@longsoho.com and that is the return address that get's rejected.

do  you have Edge Server or kind of Appliance setup as EDGE in your Email infrastructure.

I saw this issue when the User mailbox is not available on the User Import Registry which is used for Appliance for Recipient Validation. Can you may be try getting complete Undeliverable along with Email Header so i can take a look and see what server is generating an Un-deliverable/NDR ?

Server is a VM under server2013 R2 Data Center. It is server 2013R2. I configured exchange as mailbox & client access only. You can see above the ports I have mapped to the Exchange IP. Also, look at the One Drive link. This is the NDR returned back to my company's eMail that showed what happened. 

Inbound now working. I had to go to ISP to reconfigure DNS settings from sbs2008 to exchange 2013. Send & reply works on inbound. Send from outside cones inbound OK.

Now on to certificates and autodiscover to get to smart phones.